<!--

    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.

-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<HTML>
  <HEAD>
    <TITLE>Document based DOM</TITLE>
  </HEAD>
<BODY>

<h2>Document Based DOM</h2>

The package contains DOM level 1 Core and XML module
implemetation. The implementation is read-only and is on the
fly constructed from Document token chain.

<h3>Open Issues</h3>
<p>
<b>Entity references</b> cannot be properly resolved as DTD part
and all external stuff is completelly ignored. A callback
interface can be established for this purpose:

<pre>
public interface EntityReferenceResolver {
    NodeList resolveEntityReference(EntityReference ref) throws IOException;
}
</pre>

<p>
<b>Attribute values</b> should report DTD defined defaults as it
cannot be also retrieved from token chain. In this case can be also
introduced a callback or does not stay fully with DOM spec. But is
it violation of spec? We are contruction DOM without DTD knowledge
so there are not default attributes declared.

</BODY>
</HTML>
